⚡ Bolt: Fix parallel scanning serialization bottleneck#51
⚡ Bolt: Fix parallel scanning serialization bottleneck#51
Conversation
Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
💡 What: Changed
NodeModulesScannerandCacheScannerfromactortostructto enable true parallel scanning.🎯 Why: In Swift structured concurrency, using
withTaskGroupinside anactorand calling its own methods (likefindNodeModules) forces all child tasks onto the actor's single executor. This inadvertently serialized the blocking I/O operations (FileManager.default), completely preventing parallel execution. Since neither type has mutable state, converting them to structs solves this.📊 Impact: Significantly speeds up scanning (especially node_modules scanning on large file trees) by allowing tasks to truly run concurrently across the cooperative thread pool.
🔬 Measurement: Run a scan over a large directory with many
node_modules. Observe CPU core utilization (should be multithreaded) and overall wall-clock completion time.PR created automatically by Jules for task 2700170780368979529 started by @acebytes